Purpose

UIREQ-1190 - Add "Retrieval service point" filter in Request app.

Approach

This feature "Retrieval service point" is supposed to be delivered for LOC only, in the scope of Ramsons. Later from Sunflower onwards, it will be generally available. Hence existing RequestsFilters form master branch has been duplicated in src/deprecated/components folder. The is the reason that Sonar complains of high code duplication.

New implementation of Retrieval service points filter will be available from src/components/RequestsFilters.

With this approach, Retrieval service points filter is available only on environments where the flag enableEcsRequests is enabled from stripes config.

Another filter accordion is introduced to Request filters with name "Retrieval service points". It is a multi-selection filter.

A Retrieval service point is the primary SP of an item's effective location.
Hence, retrieval sps options are formed by

1. collecting primary service point of each location of a tenant
2. preparing options for retrieval service points filter from the above collection

Refs

Screenshots

Pre-Merge Checklist

Before merging this PR, please go through the following list and take appropriate actions.

• I've added appropriate record to the CHANGELOG.md
• Does this PR meet or exceed the expected quality standards?
  • Code coverage on new code is 80% or greater
  • Duplications on new code is 3% or less
  • There are no major code smells or security issues
• Does this introduce breaking changes?
  • If any API-related changes - okapi interfaces and permissions are reviewed/changed correspondingly
  • There are no breaking changes in this PR.

If there are breaking changes, please STOP and consider the following:

• What other modules will these changes impact?
• Do JIRAs exist to update the impacted modules?
  • If not, please create them
  • Do they contain the appropriate level of detail? Which endpoints/schemas changed, etc.
  • Do they have all they appropriate links to blocked/related issues?
• Are the JIRAs under active development?
  • If not, contact the project's PO and make sure they're aware of the urgency.
• Do PRs exist for these changes?
  • If so, have they been approved?

Ideally all of the PRs involved in breaking changes would be merged in the same day to avoid breaking the folio-testing environment. Communication is paramount if that is to be achieved, especially as the number of intermodule and inter-team dependencies increase.

While it's helpful for reviewers to help identify potential problems, ensuring that it's safe to merge is ultimately the responsibility of the PR assignee.